Skip to content

feat(observability): enable GlitchTip native MCP on the web container - #2

Merged
Afgan0r merged 1 commit into
masterfrom
feat/glitchtip-enable-mcp
Jun 14, 2026
Merged

feat(observability): enable GlitchTip native MCP on the web container#2
Afgan0r merged 1 commit into
masterfrom
feat/glitchtip-enable-mcp

Conversation

@Afgan0r

@Afgan0r Afgan0r commented Jun 14, 2026

Copy link
Copy Markdown
Contributor

Enables the GlitchTip native MCP server so agents can read issues/events over MCP.

Change

  • k8s/observability/91-glitchtip.yaml: add GLITCHTIP_ENABLE_MCP=True to the glitchtip-web Deployment env only (worker serves no HTTP). Root cause of the current /mcp 404 is this flag defaulting to False — image 6.1.8 already ships the feature.

Validation

  • Offline only: PyYAML multi-doc parse OK, kubectl apply --dry-run=client OK, confirmed glitchtip-web → True, glitchtip-worker → None.

Activation (staging, manual — obs is applied separately from runtime)

kubectl apply -f k8s/observability/91-glitchtip.yaml
kubectl rollout restart deployment/glitchtip-web -n error-tracking
curl -sS -o /dev/null -w '%{http_code}\n' https://errors.solid-stats.ru/mcp   # expect not-404

Then (manual, human gate): create a minimal-scope GlitchTip API token (Profile → Auth Tokens) and claude mcp add --transport http glitchtip https://errors.solid-stats.ru/mcp.

🤖 Generated with Claude Code

Set GLITCHTIP_ENABLE_MCP=True on the glitchtip-web deployment so the
native MCP server at /mcp (Streamable HTTP) is exposed; default False
returns 404. Web container only — the worker serves no HTTP. Lets local
AI agents read issues/error events from the self-hosted GlitchTip over
MCP.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@Afgan0r
Afgan0r merged commit fb847f1 into master Jun 14, 2026
3 checks passed
@Afgan0r
Afgan0r deleted the feat/glitchtip-enable-mcp branch June 14, 2026 16:53
Afgan0r added a commit that referenced this pull request Jun 15, 2026
Activate the merged errors-only Sentry SDK on staging by pinning each app to a
post-Sentry-merge image:
- server-2:        3866f6b → e31b129 (sentry #19 + parity #18/#21)
- replay-parser-2: 5e09d33c → 72116db (sentry #1)
- replays-fetcher: 7e5ca97 → 205b4cd (sentry #1 + shared-clients #2)

replays-fetcher: 7e5ca97 (F1 conditional-writes baseline) is an ancestor of
205b4cd, so the F1 fix is preserved. PARITY-COORDINATION.md is archived.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant